Skip to content

docs: Add developing modules tutorial#4155

Merged
jfy133 merged 11 commits into
mainfrom
chris-module-guide
Apr 22, 2026
Merged

docs: Add developing modules tutorial#4155
jfy133 merged 11 commits into
mainfrom
chris-module-guide

Conversation

@christopher-hakkaart
Copy link
Copy Markdown
Member

@christopher-hakkaart christopher-hakkaart commented Apr 19, 2026

  • Migrate tutorial
  • Style tutorial
  • Redirect tutorial

Closes #4145

@netlify /docs/developing/tutorials/writing-nf-core-modules/1-introduction

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 19, 2026

Deploy Preview for nf-core-docs ready!

Name Link
🔨 Latest commit fdc5ad5
🔍 Latest deploy log https://app.netlify.com/projects/nf-core-docs/deploys/69e893b32b12fc00075bc155
😎 Deploy Preview https://deploy-preview-4155--nf-core-docs.netlify.app/docs/developing/tutorials/writing-nf-core-modules/1-introduction
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 19, 2026

Deploy Preview for nf-core-main-site ready!

Name Link
🔨 Latest commit fdc5ad5
🔍 Latest deploy log https://app.netlify.com/projects/nf-core-main-site/deploys/69e893b33a326600090a9600
😎 Deploy Preview https://deploy-preview-4155--nf-core-main-site.netlify.app/docs/developing/tutorials/writing-nf-core-modules/1-introduction
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@christopher-hakkaart
Copy link
Copy Markdown
Member Author

@nf-core-bot fix linting

Copy link
Copy Markdown
Member

@jfy133 jfy133 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got side tracked and have to get kits up now, but conceptual question on first page for consideration

@christopher-hakkaart
Copy link
Copy Markdown
Member Author

Also - feel free to push changes. I'm not attached to anything strongly.

Copy link
Copy Markdown
Member

@jfy133 jfy133 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Finished up to page 3, will continue from 4 onwards when I have time


The following diagram shows how these files relate to each other:

<img width=80% alt="Diagram showing how the execution, documentation, and testing files in an nf-core module relate to each other." src="../../../../../assets/images/tutorials/training/nf-core-module-file-relationship.png">
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't working...

Copy link
Copy Markdown
Member

@jfy133 jfy133 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Chapter 5 review done. Continuing next time from chapter 6

Co-authored-by: James A. Fellows Yates <jfy133@gmail.com>
Copy link
Copy Markdown
Member

@jfy133 jfy133 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Finished!

test("sarscov2 - fastq - bakta annotation input")
```

In the `when` block, declare each input channel using `input[index]` notation (`input[0]` for the first, `input[1]` for the second, and so on). The block accepts standard Nextflow code — channel factories, operators, and so on — as you would use in a pipeline. Make sure each `input[]` matches the channel structure of your module, including any meta map:
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In the `when` block, declare each input channel using `input[index]` notation (`input[0]` for the first, `input[1]` for the second, and so on). The block accepts standard Nextflow code — channel factories, operators, and so on — as you would use in a pipeline. Make sure each `input[]` matches the channel structure of your module, including any meta map:
In the `when` block, declare each input channel using `input[index]` notation (`input[0]` for the first, `input[1]` for the second, and so on).
The block accepts standard Nextflow code — channel factories, operators, and so on — as you would use in a pipeline.
Make sure each `input[]` matches the channel structure of your module, including any meta map:

Copy link
Copy Markdown
Member

@jfy133 jfy133 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Finished!

jfy133 added 3 commits April 22, 2026 09:57
Co-authored-by: James A. Fellows Yates <jfy133@gmail.com>
Co-authored-by: James A. Fellows Yates <jfy133@gmail.com>
Co-authored-by: James A. Fellows Yates <jfy133@gmail.com>
@jfy133
Copy link
Copy Markdown
Member

jfy133 commented Apr 22, 2026

@nf-core-bot fix linting

@jfy133 jfy133 self-requested a review April 22, 2026 09:28
Copy link
Copy Markdown
Member

@jfy133 jfy133 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jfy133 jfy133 merged commit 03168e6 into main Apr 22, 2026
13 checks passed
@jfy133 jfy133 deleted the chris-module-guide branch April 22, 2026 09:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[404] Page not found: https://www.google.com/

3 participants